Generation And Management Of Network Connectivity Information

ABSTRACT

Aspects of the disclosure relate to generation of network topology information for a network of assets, and management of such information. The management can comprise analysis and/or diagnostics of topology condition of a plurality of assets. In addition or in the alternative, the management can comprise consolidation of at least a portion of the network topology information in a data layer of the network of assets, or a network functionally coupled thereto. Integration of at least some of the network topology information with higher network layers also is disclosed.

CROSS REFERENCE TO RELATED APPLICATION

This application is a Continuation of U.S. Non-Provisional applicationSer. No. 13/736,172 filed Jan. 8, 2013, herein incorporated by referencein its entirety.

BACKGROUND

Conventional approaches to generation of network topology information,e.g., location information, connectivity information, or a combinationthereof, in a network of functional elements rely extensively on humanintervention and, as a result, are error prone and generally static.Such approaches fail to provide current network topology information ina cost effective manner. In addition, such approaches generally fail tobe integrated across various layers of a network of functional elements.

SUMMARY

It is to be understood that this summary is not an extensive overview ofthe disclosure. This summary is exemplary and not restrictive, and it isintended to neither identify key or critical elements of the disclosurenor delineate the scope thereof. The sole purpose of this summary is toexplain and exemplify certain concepts of the disclosure as anintroduction to the following complete and extensive detaileddescription.

The disclosure relates to, in one aspect, generation of network topologyinformation for a network of assets, and management of such information.The management can comprise analysis and/or diagnostics of topologycondition of a plurality of assets. In addition or in the alternative,the management can comprise consolidation of at least a portion of thenetwork topology information into a data layer of the network of assetsor a network functionally coupled thereto. Integration of at least someof the network topology information with higher network layers also iscontemplated.

Some embodiments of the disclosure provide various advantages whencompared to conventional approaches for generation of network topologyinformation and management thereof. For example, one embodiment of thedisclosure provides access to connectivity information associated withall or most all tagged equipment at a user site (e.g., a residentialuser or customer site, or a commercial user or customer site). As aresult, the disclosure can permit addressing operational issuesexpeditiously, resulting in a reduction of cost and time associated withnetwork service, and increased quality of customer service and increasedcustomer satisfaction. For another example, another aspect of thedisclosure permits integration of network topology information withadministrative network layers, thus permitting remote assessment ofnetwork performance, with the ensuing reduction of costs associatedwith, for example, visitations of field facilities (e.g., a hub, anaggregator site, a base station site, or the like) for assessment andmaintenance. For yet another example, other embodiments of thedisclosure can permit monitoring of asset connectivity (e.g., fiberoptic connectivity) in nearly real-time, according to a predeterminedschedule, or in response to specific events. For example, near real-timemonitoring can be provided for events such as deployment changes in anetwork comprising tagged assets, or delivery of status messages tospecific portions of the network.

Additional aspects or advantages of the subject disclosure are set forthin part in the description which follows, and in part will be obviousfrom the description, or may be learned by practice of the subjectdisclosure. The advantages of the subject disclosure can be realized andattained by means of the elements and combinations particularly pointedout in the appended claims. It is to be understood that both theforegoing general description and the following detailed description areexemplary and explanatory only and are not restrictive of thedisclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The annexed drawings are an integral part of the subject disclosure andillustrate exemplary embodiments thereof. Together with the descriptionset forth herein and the claims appended hereto, the annexed drawingsserve to explain various principles, features, or aspects of the subjectdisclosure.

FIG. 1 illustrates an example system in accordance with one or moreaspects of the disclosure.

FIG. 2 depicts an example link connecting network devices in accordancewith one or more aspects of the disclosure.

FIG. 3 illustrates an example system in accordance with one or moreaspects of the disclosure.

FIG. 4 illustrates an example computing device in accordance with one ormore aspects of the disclosure.

FIG. 5 illustrates an example computing device in accordance with one ormore aspects of the disclosure.

FIG. 6A illustrates an example wireless device and respective functionalelements in accordance with one or more aspects of the disclosure.

FIG. 6B illustrates an example wireless device and respective functionalelements in accordance with one or more aspects of the disclosure.

FIG. 7A illustrates an example wireless device and respective functionalelements in accordance with one or more aspects of the disclosure.

FIG. 7B illustrates an example wireless device and respective functionalelements in accordance with one or more aspects of the disclosure.

FIG. 8A illustrates an example wireless device and respective functionalelements in accordance with one or more aspects of the disclosure.

FIG. 8B illustrates an example wireless device and respective functionalelements in accordance with one or more aspects of the disclosure.

FIG. 9 is a flowchart illustrating an example method in accordance withone or more aspects of the disclosure.

FIG. 10 is a flowchart illustrating an another example method inaccordance with one or more aspects of the disclosure.

FIG. 11 is a flowchart illustrating an another example method inaccordance with one or more aspects of the disclosure.

FIG. 12 is a flowchart illustrating an another example method inaccordance with one or more aspects of the disclosure.

DETAILED DESCRIPTION

The various aspects described herein can be understood more readily byreference to the following detailed description of exemplary embodimentsof the subject disclosure and to the annexed drawings and their previousand following description.

Before the present systems, articles, apparatuses, and methods aredisclosed and described, it is to be understood that the disclosure isnot limited to specific systems, articles, apparatuses, and methods forgeneration of network topology information for a network of assets, andmanagement of such information. It is also to be understood that theterminology employed herein is for the purpose of describing particular,non-exclusive embodiments only and is not intended to be limiting.

As used in the specification and the appended claims, the singular forms“a,” “an” and “the” include plural referents unless the context clearlydictates otherwise. Ranges may be expressed herein as from “about” oneparticular value, and/or to “about” another particular value. When sucha range is expressed, another embodiment includes from the oneparticular value and/or to the other particular value. Similarly, whenvalues are expressed as approximations, by use of the antecedent“about,” it will be understood that the particular value forms anotherembodiment. It will be further understood that the endpoints of each ofthe ranges are significant both in relation to the other endpoint, andindependently of the other endpoint.

As utilized in this specification and the annexed drawings, the terms“system,” “layer,” “component,” “unit,” “interface,” “platform,” “node,”“probe,” “function” and the like are intended to include acomputer-related entity or an entity related to an operational apparatuswith one or more specific functionalities, wherein the computer-relatedentity or the entity related to the operational apparatus can be eitherhardware, a combination of hardware and software, software, or softwarein execution. Such entities also are referred to as “functionalelements.” As an example, a unit can be, but is not limited to being, aprocess running on a processor, a processor, an object (metadata object,data object, signaling object), an executable computer program, a threadof execution, a program, a memory (e.g., a hard-disc drive), and/or acomputer. As another example, a unit can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry which is operated by a software application or afirmware application executed by a processor, wherein the processor canbe internal or external to the apparatus and can execute at least aportion of the software application or the firmware application. As yetanother example, a unit can be an apparatus that provides specificfunctionality through electronic functional elements without mechanicalparts, the electronic functional elements can include a processortherein to execute software or firmware that provides, at least in part,the functionality of the electronic functional elements. The foregoingexamples and related illustrations are but a few examples and are notintended to be limiting. In addition, while such illustrations arepresented for a unit, the foregoing examples also apply to a system, alayer, a node, an interface, a function, a component, a platform, andthe like. It is noted that in certain embodiments, or in connection withcertain aspects or features such embodiments, the terms “system,”“layer,” “unit,” “component,” “probe,” “interface,” “platform” “node,”“function” can be utilized interchangeably.

Throughout the description and claims of this specification, the words“comprise,” “include,” and “having” and their variations, such as“comprising” and “comprises,” “include” and “including,” “having” and“has,” mean “including but not limited to,” and are not intended toexclude, for example, other units, nodes, components, functions,interfaces, actions, steps, or the like. “Exemplary” means “an exampleof” and is not intended to convey an indication of a preferred or idealembodiment. “Such as” is not used in a restrictive sense, but forexplanatory purposes.

Disclosed are components that can be utilized to perform the disclosedmethods, devices, and/or systems. These and other components aredisclosed herein, and it is understood that when combinations, subsets,interactions, groups, etc. of these components are disclosed that whilespecific reference of each various individual and collectivecombinations and permutation(s) of these may not be explicitlydisclosed, each is specifically contemplated and described herein, forall methods, devices, and/or systems. This applies to all aspects of thesubject disclosure including steps, or actions, in the disclosedmethod(s). Thus, if there are a variety of additional steps, or actions,that can be performed, then it is understood that each of suchadditional steps, or actions, can be performed with any specificembodiment or combination of embodiments of the disclosed methods.

As it will be readily appreciated, in one aspect, the methods, devices,and/or systems of the disclosure can take the form of an entirelyhardware embodiment, an entirely software embodiment, or an embodimentcombining software and hardware aspects. In an additional or alternativeaspect, the methods, devices, and/or systems can take the form of acomputer program product on a computer-readable storage medium havingcomputer-readable program instructions (e.g., computer software)embodied in the storage medium. More particularly, the disclosedmethods, devices, and/or systems can take the form of web-implementedcomputer software. Any suitable computer-readable storage medium can beutilized including hard disks, CD-ROMs, optical storage devices, ormagnetic storage devices.

Embodiments of the methods and systems are described below withreference to block diagrams and flowchart and/or call-flow illustrationsof methods, systems, apparatuses and computer program products. It willbe understood that each block of the block diagrams and flowchartillustrations, and combinations of blocks in the block diagrams andflowchart illustrations, respectively, can be implemented by computerprogram instructions. Such computer program instructions may be loadedonto a general purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions which execute on the computer or other programmabledata processing apparatus create a means for implementing the functionsspecified in the flowchart block or blocks.

These computer program instructions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including computer-readableinstructions for implementing the function specified in the flowchartblock or blocks. The computer program instructions also can be loadedonto a computer or other programmable data processing apparatus to causea series of operational steps, or acts, to be performed on the computeror other programmable apparatus to produce a computer-implementedprocess such that the instructions that execute on the computer or otherprogrammable apparatus provide steps for implementing the functionsspecified in the flowchart block or blocks.

Accordingly, blocks of the block diagrams and flowchart illustrationssupport combinations of means for performing the specified functions,combinations of steps for performing the specified functions and programinstruction means for performing the specified functions. It also willbe understood that each block of the block diagrams and flowchartillustrations, and combinations of blocks in the block diagrams andflowchart illustrations, can be implemented by special purposehardware-based computer systems that can perform the specified functionsor steps, or combinations of special purpose hardware and computerinstructions.

Reference will now be made in detail to the various embodiments andrelated aspects of the subject disclosure, examples of which areillustrated in the accompanying drawings and their previous andfollowing description. Wherever possible, the same reference numbers areused throughout the drawings to refer to the same or like parts.

The disclosure identifies and addresses, in one aspect, the issue ofinadequacy and failure-propensity of human intervention and ad-hocapproaches that are commonly utilized to generate network topologyinformation. Such approaches generally rely on bookkeeping practicesthat are susceptible to “authorship collision” in that a first agent(e.g., a field engineer, a home owner, or the like) can generate networktopology information for a specific network deployment according to afirst documentation protocol, whereas a second agent can generatenetwork information topology according to a second protocol, whereinsuch protocols can have different notations for records, can introducespecific bookkeeping errors, and/or can mutually modify the content ofthe network topology information. Thus, the network topology informationgenerated by the first agent (or first author) can be incompatible (orcan “collide”) with the network topology information generated by thesecond agent (or second author). In addition or in the alternative, anad-hoc approach can include reverse-engineering actions associated withinspection of connectivity between different network devices and, as aresult, the approach be affected by “reconstruction blockade,” whichrefers to the inability to implement the ad hoc approach for generationof network topology information in view that a network deployment may berendered inoperable in response to implementation of the approach. Forinstance, an active connection in a network deployment (e.g., a plumbingconnection, an electricity connection, a gas line, etc.) may not bedisconnected in order to obtain connectivity information and revealspecific coupling amongst two or more network devices. Furthermore or asanother alternative, ad hoc approaches can be affected by “directionalmyopia” in that reverse engineering the connectivity of a network devicecan be primarily local and can fail to reveal connectivity with adistant network device. As a result of the directional myopia, ad hocapproaches generally fail to reveal how a physical link (such as anoptic fiber, a wire, or a pipe) is physically routed.

As described in greater detail below, the disclosure related, in oneaspect, to generation of network topology information for a network ofassets, and management of such information. As it will be apparent fromthe disclosure, the described generation of network topology informationlargely is immune to authorship collision, reconstruction blockade,and/or directional myopia. The management can comprise analysis and/ordiagnostics of topology condition of a plurality of assets. In additionor in the alternative, the management can comprise consolidation of atleast a portion of the network topology information into a data layer ofthe network of assets or a network functionally coupled thereto.Integration of at least some of the network topology information withhigher network layers also is contemplated. Certain functional elementsof the subject disclosure can be implemented (e.g., performed) bysoftware, hardware, or a combination of software and hardware.Functional elements of the various embodiments described in the presentspecification and illustrated in the annexed drawings can be employed inoperational environments (access network, telecommunication network,signaling network, utility network, etc.) that can include, for example,digital equipment, analog equipment, or both, wired or wirelessequipment, etc.

FIG. 1 is a block diagram of an example system 100 that permitsgeneration and/or management of network topology information inaccordance with one or more aspects of the disclosure. The examplesystem 100 can comprise a plurality of network devices positioned atspecific locations. As illustrated, three network devices 110-130 can bepositioned at respective locations 140 ₁ (location I), 140 ₂ (locationII), and 140 ₃ (location III). In certain embodiments, location I,location II, and location III can be part of a common area, such as adwelling, a transportation vehicle, or an enterprise facility, thecommon area can be open (e.g., a park, a parking lot) or semi-open (acity recreation center, an event space, or a cable headend, forexample). Examples of the dwelling can comprise a skyscraper, anapartment building, and the like. Examples of the transportation vehiclecan comprise an aircraft carrier, an airplane, a cruise ship, an oiltanker, and the like. Examples of the enterprise facility can comprise afactory, or an oil refinery, a nuclear power plant, a central office ofa telephone company, a hospital, and the like. In other embodiments, oneof the locations 1401-140 ₃ can be geographically distant from the othertwo locations. For example, in a scenario in which the network devicesare contained within a service network (such as a content deliverynetwork), locations 140 ₁ and 140 ₂ can be within customer premises,whereas location 140 ₃ can be situated at a last-mile aggregator. Foranother example, location 140 ₁ can be the location of a mains circuitpanel, whereas locations 140 ₂ and location 140 can be situated atdifferent positions within a factory floor.

Each one of the network devices can comprise one or more connectors orports, referred to collectively as members, e.g., structural features orfunctional elements that can permit coupling to other networkdevices(s). For example, network device 110 can include nine members 112₁-112 ₉, network device 120 can include two members 122 ₁ and 122 ₂, andnetwork device 130 can include eight members 132 ₁-132 ₈. Asillustrated, member 112 ₁ is functionally coupled to member 132 ₃ via alink 116, member 112 ₃ is functionally coupled to 132 ₁ via a link 118,and member 1126 is coupled to 1221 via a link 114. In aspect, a memberin a network device that is not coupled to another member in anothernetwork device can be referred to as an “in-use member,” whereas members(such as member 122 ₂ or member 112 ₉) that are not coupled to othermembers can be referred to as “non-used” members.

Each of the links 114, 116, and 118 can have a wireless tag unit (alsoreferred to as wireless tag) fitted at each end of a physical link(comprising certain physical medium) that forms the link. In one aspect,each of the wireless tags can contain location information associatedwith the respective network device that the wireless tags are coupledto. The location information (e.g., a position vector (x,y,z)) canpermit identifying the relative positioning of the ends of the physicallink (e.g., a wire, an optic fiber, a pipe, etc.). Such wireless tagsare represented as white boxes in FIG. 1, and example embodiment 200 inFIG. 2 illustrates tagging of end-points of a link. In such embodiment,a first wireless tag 218 a can be attached to a physical link 214 (e.g.,a wire, a pipe, an optic fiber, or the like) and coupled to a firstmember 210, and a second wireless tag 218 b also is attached to thephysical link 214 and coupled to a second member 220. In one embodiment,the wireless tag 218 a can be or can comprise a male-plug proximityradiofrequency identification (RFID) tag coupled (e.g., connected) to afemale-connector proximity RFID tag included in the member 210.Similarly, in such embodiment, the wireless tag 218 b also can be amale-plug proximity RFID tag that can be coupled to a female-connectorproximity RFID tag included in the member 220. Such proximity RFID tagscan be passive tag units or battery-assisted tag units.

In addition or in the alternative, a link, such as link 116, can haveone or more wireless tags, e.g., wireless tags 117 a-117 c, attached atrespective positions along the link. The one or more wireless tags cancontain location information (e.g., a “fix” for each wireless tag) thatcan permit generating routing information associated with the pathbetween a first end of a physical link and a second end of the physicallink. For example, location I and location II can be situated indifferent environments, such as different rooms or floors of a facility,and the path associated with the link 116 can proceed into a ceiling,along with many other wires, fibers, cables, through walls, and/orunderground.

In one aspect, deployment of a plurality of wireless tags, such aswireless tags 117 a-117 c, in a link connecting a first network deviceand a second network device can address the issue of directional myopia,particularly, yet not exclusively, in complex sites, by providing (e.g.,communicating to the wireless probe 150) information associated with apath between such network devices. Each of the plurality of wirelesstags can reference at least one member of the first network device andat least one member of the second network device. In a scenario in whicha connection proceeds through walls and rooms and different floors orrisers, at least a portion of the plurality of wireless tags cantransmit location information to the wireless probe 150, which canprocess such information and can generate data objects indicative ofdirections to span the path from the first network device to the secondnetwork device. The wireless probe 150 can supply such data objects tothe repository 196. For instance, such directions can convey that thepath can be spanned by turning left through this hall, right down thecorridor, to this elevator, to this floor to this corridor, to thisroom, and so forth.

As the wire was initially run, it could also be scanned into thedatabase. When it got to the far end, that device or connection wouldalso have RFID on its female port. When it's plugged in and scanned, itwould also enter into the database as a connection that has been made.The (x, y, z) coordinates of the 2 end-points and/or the informationassociated with the path between the two ends can be available.Accordingly, with the two end-point (x, y, z) coordinates, the straightdistance and direction between the two end-points can be available.

It should be appreciated that, in one aspect, such directionalinformation can provide rich details of the connectivity between networkdevices in networks of functional elements. Detailed informationassociated with such connectivity can permit faster response time to anetwork malfunction or maintenance event despite prior experience ofpersonnel (e.g., a network employee, a vendor, or the like) servicingthe location associated with the event.

In certain scenarios, network devices and/or links can be legacy networkdevices or legacy links that can be retrofitted with wireless tags. Insuch scenarios, a wireless tag can be added (or incorporated) to alegacy network device or a legacy link. It should be appreciated that insuch scenarios connectivity may not be straightforward due toinfrastructural elements (such as an item embedded into a wall,fire-stopper materials, and the like). In other scenarios, wireless tagscan be incorporated in a bottom-up manner, with one or more wirelesstags being incorporated to each network device and/or link that is addedinto a network deployment (or related network topology).

Network devices and links are collectively referred to herein as“assets.” The assets can be specific to the network deploymentcomprising the wireless tags. In one aspect, a link can be embodied inor can comprise a specific physical medium that can permit functionalcoupling and/or structural coupling between two assets. For example, anetwork deployment can be a plumbing network in which the links can beembodied in or can comprise pipes of one or more types (PVC pipe, metalpipe, etc.), and the network device can include fittings, valves, flowmeters, pressure meters, and/or water heating equipment.

As illustrated in FIG. 1, a wireless probe 150 can communicatewirelessly with a wireless tag coupled to a member, e.g., a port, in anetwork device, such as a router, a television set, or personalcomputer. In addition or in the alternative, the wireless probe 150 cancommunicate with a wireless tag attached to a link (e.g., link 114) thatcouples two members of disparate network devices. In one aspect, thewireless probe 150 can communicate wirelessly via wireless link(s)(e.g., link 160, link 170, and/or link 180) in accordance with apoint-to-point radio technology protocol, even though other radiotechnology protocols can be utilized for communication. In anotheraspect, communication between a wireless tag and the wireless probe 150or a component thereof can be effected in accordance with one or morepacket-switched protocols, such as Ethernet protocol format; internetprotocol (IP) format, such as IPv4 and IPv6, or the like; TCP/IP; userdatagram protocol (UDP) format, HTTP, simple object access protocol(SOAP), simple network management protocol (SNMP), or the like.

As described herein, the wireless probe 150 can communicate with thewireless tags (represented with small, open rectangles) in networkdevice 110 via wireless links 170, which comprises an upstream link (oruplink (UL) and a downstream link (or downlink (DL)). In addition, thewireless probe 150 can communicate with the wireless tag in networkdevice 120 and the wireless tags in network device 130 via wirelesslinks 160 and 180, respectively. In certain embodiments, the wirelesslinks 160, 170, and 180 can transport information coded and multiplexedaccording to a common radio technology protocol. In such embodiments,differences among such wireless links can originate from transmissionconditions of the air interface, such as signal-to-noise ratio, presenceor absence of scattering, or the like. In addition or in thealternative, in embodiments in which the wireless probe 150 can operatein multiple modes (e.g., operate in accordance with various radiotechnology protocols), two or more of the wireless links 160, 170, or180 can be different due to difference(s) in the radio technologyprotocol utilized to exchange information with a wireless tag in networkdevices 110, 120, or 130. Moreover or as another alternative, a wirelesslink that permits communication between the wireless probe 150 and awireless tag in a network device can be specific to such wirelessdevice. Thus, in one aspect, the wireless probe 150 can communicate viafirst wireless links with a first wireless device (132 ₁) and via secondwireless links with a second wireless device (132 ₃) in the networkdevice. It should be appreciated that communication via differentwireless links can permit communication with different types of wirelesstags, including present-generation wireless tags and prior-generation(or legacy) wireless tags, for example.

As part of communication with a wireless tag coupled to a networkdevice, in one aspect, the wireless probe 150 can access informationretained in the wireless tag. In one scenario, the wireless probe 150can transmit electromagnetic (EM) radiation (e.g., EM radiationmodulated and encoded into one or more packets of information) to thewireless tag, which can include circuitry that can energize the wirelesstag in response to receiving the EM radiation. Upon or after beingenergized, the wireless tag can transmit information contained therein,the information can include, for example, location information (e.g.,data and/or metadata indicative of position) and/or connectivityinformation associated with at least the wireless tag. The informationthat is transmitted can be collected by the wireless probe 150.

In a new build scenario, a local origin point—a (0,0,0) point (x,y,z)coordinate reference can be selected and tagged with a wireless devicefor a site. This would be logically tied to the actual GPS location in adatabase (e.g., location information 356). The wireless probe 150 canprobe the location of that local origin point and compare and referenceto such origin all subsequent local connections to be determined. In oneaspect, the first network device (e.g., a device) can be placed at thatsite. As described herein, the network device, which can be a subtendingorigin point, and can be usually female connection points, can havewireless tags (e.g., passive RFID tags) coupled thereto. The wirelessprobe 150 can then scan the wireless tags (e.g., passive RFID tags) ofthe device and the ports, causing such wireless tags to supply (e.g.,broadcast) identification and/or location information. As describedherein, the wireless probe 150 can transmit such information, comprisingtheir (x, y, z) coordinates into the database.

In one aspect, for a network device having one or more members that isincorporated into a network of functional elements (e.g., the set ofnetwork devices 110, 120, and 130), a first wireless scan of the networkdevice can indicate that the network device has at least one (e.g., one,two, more than two, or all) of the one or more members is unconnected.As part of incorporation into such network, a first connection can bemade. In one aspect, a male end of a connector, such as link, that isconnected to a member of the network device can have a wireless tag thatcan detect, via proximity detection, an associated female wireless tag.In response to a wireless probe (e.g., 150) scanning the network device(e.g., a device with several ports), the wireless tag associated to themale end and the wireless tag associated with the female end cancommunicate network topology information, which the wireless probe cansupply to network repository (e.g., repository 196). The networktopology information can comprise connectivity information thatindicates that male end and the female are paired—e.g., a good physicalconnection exists between such elements. In one aspect, the far end ofthe connector (e.g., wire, pipe, fiber etc.) also can have anotherpaired male-female coupling. In a scenario in which the transmittedpower for EM radiation emitted by the wireless probe is sufficientlyelevated and/or the far end connector is within range of the emitted EMradiation, wireless device associated with male and female ends cansupply network topology information to the wireless probe. In oneaspect, the wireless probe can supply network information associatedwith the far end of the connector to the network repository. Suchnetwork information can comprise data and/or metadata indicative of theconnector having two logically tied ends. One of such ends (e.g., thefar end) can be classified in the network repository as plugged in, oractive, whereas the other end, e.g., the end at the network device, canbe classified as unplugged, or inactive at the time of the scan. Itshould be appreciated that after connection, in response to a scan bythe wireless probe, both end of the connector can be classified asplugged-in.

In certain embodiments, a wireless tag (e.g., 218) can be sufficientlycomplex—e.g., it can include a dedicated power source and a processor—tobroadcast information contained in the wireless tag. The information canbe broadcast at specific intervals (e.g., at periodic intervals, atscheduled instants, or in response to an event). As described herein,such information can comprise location information and/or connectivityinformation associated with the wireless tag. In such embodiments, thewireless probe 150 can collect (e.g., receive and process) the broadcastinformation instead of actively probing the wireless tag. Thus, thewireless probe 150 operates as a monitoring device.

It should be appreciated that in certain scenarios, deployment of awireless tag that can broadcast information contained therein can permitto communicate location information and/or connectivity information ofthe wireless tag from a position that may not permit the wireless probe150 to probe such tag and, in response collect the location and/orconnectivity information. For instance, a network device (e.g., thebackplane of a quadrature amplitude modulation (QAM) node, a utilitymeter, or an industrial controller) can be positioned in a manner thatother network devices (e.g., equipment) can block line-of-sight (LOS)transmission of EM radiation that can probe a wireless tag coupled to amember (e.g., a connector in the backplane or in the utility meter).Thus, if sufficient scattering of the EM radiation prevents the wirelessprobe 150 from probing such wireless tag, then location informationand/or connectivity information associated with the network device canbe unavailable. Yet, broadcast information from such wireless tag (e.g.,wireless tag 132 ₁) can be collected by the wireless probe 150, with theensuing availability of location information and/or connectivityinformation.

In certain embodiments, a wireless tag can have sufficient complexity toperform proximity detection in response to the wireless tag beingenergized by the wireless probe 150. For example, the wireless tag cancomprise a processor or other specific circuitry that can enableproximity detection. It should be appreciated that, in certainscenarios, proximity detection can be implemented at least during theperiod that two or more wireless tags (e.g., wireless tag 218 and matedcounterpart) are energized by the wireless probe 150. The proximitydetection can permit identifying the presence of other wireless tag(s)in the vicinity of the wireless tag. Such vicinity can be determined bya detection range based at least on the sensitivity of the wireless tagto RF signal transmitted by the other wireless tag(s). In oneimplementation, the detection range can be short-ranged in order toincrease the likelihood that a proximal wireless tag that is detected isa mated wireless tag. In one aspect, the proximity detection includescollection of RF signal at the wireless tag, and determination ofstrength of the collected signal. For a strength that is at leastsubstantially equal to a predetermined threshold, the wireless tag canestablish that a proximal wireless tag is detected. In addition, as partof the proximity detection, the wireless tag can decode one or more ofan identifier indicative of an identity of a detected proximal wirelesstag or an identifier indicative of a logical address (e.g., an IPaddress, such as IPv6 address) of the wireless tag, wherein suchidentifiers are transported (or communicated) in the RF signal receivedfrom the proximal device. In response to detection of a proximalwireless tag, in one aspect, the wireless tag that performs thedetection can transmit, to the wireless probe 150, informationindicative of the wireless being a mated tag. In another aspect, thewireless tag that performs the detection can transmit (e.g., broadcast)one or more of an identifier indicative of the identity of such tag oran identifier indicative of a logical address thereof.

In certain scenarios, such as fiber optics splice cases, or welds orsoldering, where wiring, metal, or fibers may need to be stripped backfrom a proximity point while a connection is rejoined, welded, or glued,the tags may need to be able to have 2 points to which they areattached, so that they can slide backward from the stripping orconnection point, then forward to again to re-mate together upon the newconnection to re-establish a new proximity detection point forrescanning.

As described herein, the wireless probe 150 can receive locationinformation and/or connectivity information from one or more wirelesstags coupled to one or more network devices and, based at least on suchinformation, the wireless probe 150 can supply (e.g., transmit, processand transmit, or the like) topology information 184 of a network ofnetwork devices comprising network devices 110-130 to a topology server194. As illustrated, the topology server 194, can be part of a network190 (e.g., a service network, such as a cable television network, a dataservice network, a utility service network, combinations thereof, or thelike). In one aspect, the topology information 184 can comprise one ormore data objects indicative of the location information and/orconnectivity information. The one or more data objects can comprise, inone implementation, information indicative of one or more network deviceIDs, network devices type, and/or network device location. In otherimplementations, the one or more data objects also can compriseinformation indicative of at least one logical address associated withat least one wireless tag.

To describe in greater detail the exchange of topology information amonga wireless tag and the wireless probe 150, FIG. 3 illustrates ahigh-level block diagram of an example system 300 that enablesgeneration and management of network topology information in accordancewith one or more aspects of the disclosure.

As illustrated, the example system 300 comprises a wireless tag 302 athat can be functionally coupled to the wireless probe 150 via wirelesslink(s) 315, which can permit the wireless tag 302 a to exchangeinformation with the wireless probe 150. In one aspect, the informationcan be transported via wireless link(s) 315 as part of signaling 317and/or data 319. To exchange information with the wireless probe 150, inone aspect, the wireless tag 302 a can comprise a tag radio unit 306that can receive EM radiation. As described herein, in response toreceiving the EM radiation, a power unit 308 can be energized, therebysupplying power to one or more of a tagging unit 304, a proximity(proxim.) detection unit 309, or the tag radio unit 306. In one aspect,upon or after being powered on, the tagging unit 304 can accessinformation (e.g., data or metadata, or both) in memory 310, and cansupply (e.g., transmit, process and transmit, or the like) at least aportion of such information to the tag radio unit 306. In anotheraspect, in response to receiving information, the tag radio unit 306 canprovide, or supply, the information to the wireless probe 150. In oneembodiment, the EM radiation can embody the signaling 317, and the tagradio unit 308 can comprise an antenna that can collect at least aportion of the signaling 317, and can inductively generate anelectromotive force (EMF) that can energize the power unit 308. Itshould be appreciated that in additional or alternative embodiments, inorder to energize the power unit 308, the wireless tag 302 a can receivethe EM radiation without receiving signaling 317 and/or data 319. Insuch embodiments, the wireless link(s) 315 can have an UL without a DL,wherein the UL can permit transmission of information from the wirelesstag 302 a to the wireless probe 150. Absence of a DL can simplifytransmission of EM radiation from the wireless probe 150 to the wirelesstag 302 a because such radiation, in one aspect, need not be processed(e.g., modulated and/or encoded) for transmission as signaling 317and/or data 319. In such alternative or additional embodiments, the tagradio unit 308 can comprise an antenna or a pick-up coil that cancollect the EM radiation and energize the power unit 308.

As described herein, the proximity detection unit 309 can performproximity detection in accordance with aspects described herein. Incertain embodiments, the proximity detection unit 309 can be embodied inor can comprise one or more micro antennas (e.g., parabolic antenna(s))and circuitry functionally coupled thereto that can permit detection ofthe strength of wireless signal received from a wireless tag, such aswireless tag 302 b. Such wireless signal can be received via a wirelesslink 342. In addition or in the alternative, the proximity detectionunit 309 can receive (e.g., decode) information indicative of, forexample, an ID of the wireless tag (e.g., 302 b) from which the wirelesssignal is received. In one embodiment, the proximity unit 309 can beintegrated into the memory 310.

In one embodiment, the wireless tag 302 a can be re-writable, having oneor more pins (not depicted) for programming such tag and variousinformation contained therein. In an additional or alternativeembodiment, the wireless tag 302 also can have one or more pins (notdepicted) for testing such tag (for example, probing the integrity ofavailable information).

The information that the wireless tag 302 a can transmit to the wirelessprobe 150 can be retained in the memory 310 and can comprise one or moreof location information, identifying information, or connectivityinformation. In one aspect, the identification information cancharacterize the wireless tag 302 a and/or the location thereof. Asillustrated, the location information can be retained in a memoryelement 312 represented with a block labeled “location.” The memoryelement 312 can be referred to as location 312 and can be embodied in orcan comprise a register, a memory page, a file, a database, anycombination thereof, or the like. The location 312 can comprise a datastructure indicative of a location of wireless tag 302 a, wherein thelocation can be conveyed with varying degrees of resolution depending atleast in part on the network device (e.g., network device 120) to whichthe wireless tag 302 a is coupled to. In one aspect, the resolution canincrease with the density of network devices being tagged with wirelesstags. In addition, in the illustrated example system 300, theidentifying information can be retained (e.g., encoded) in severalmemory elements: (1) one or more memory elements 311 that can compriseone or more names or identifications (ID(s)) associated with thewireless tag 302 a and/or an asset coupled thereto, such name(s) orID(s) can be configured according to one or more specific namingconventions; (2) a memory element 313 that can comprise data and/ormetadata indicative of a type of network device being tagged by thewireless tag 302 a, and/or indicative of whether the wireless tag 302 ais mated to another wireless tag (e.g., wireless tag 302 b); (3) one ormore memory elements 314 that can comprise data indicative of one ormore logical addresses (e.g., IP address(es), such as IPv6 address, orthe like); and (4) a memory element that can comprise connectivityinformation indicative of one or more assets to which the wireless tagis coupled to, e.g., the connectivity information can indicate a link towhich the wireless tag 302 a is attached to, a first member coupled to afirst end of the link, and a second member coupled to a second end ofthe link. It should be appreciated that the naming convention can beestablished by one or more agents (human or machine), such as amanufacturer of the wireless tag 302 a; a vendor of the wireless tag 302a; an administrator of a network comprising a network device tagged withthe wireless tag 302 a; or the like. It should also be appreciated thatthe connectivity information can include a logical variable indicativeof attachment status, e.g., such variable can indicate if the wirelesstag 302 a is coupled to an in-use member or to a non-used member.

As described herein, the wireless probe 150 can receive information froma wireless tag, such as wireless tag 302 a or wireless tag 302 b. In oneaspect, the wireless probe 150 can comprise a probe radio unit 324 thatcan transmit EM radiation to the wireless tag 302 a to energize it and,in response, to receive information from the wireless tag 302 a. In oneaspect, the information can comprise at least a portion of the locationinformation and/or the identifying information available in the wirelesstag 302 a. Such information can be received as part of data 319 via theUL included in the wireless link(s) 315. In one aspect, the radio probeunit 324 can supply at least a portion of the received information to atopology constructor 328 that can provide (e.g., generate or update)topology information, and can retain such information in one or moreelements 335 represented with a block labeled “topology info.” in memory334. The memory element(s) 335 can be referred to as topology info. 335and can be embodied in or can comprise a register, a memory page, afile, a database, any combination thereof, or the like.

In certain implementations, the topology information can comprisenetwork location information and network connectivity information. Inone aspect, the network topology information can include locationinformation of the wireless tag 302 a and/or identifying informationthereof. In another aspect, the network connectivity information caninclude data indicative of a relationship between the location ofwireless tag 302 a and a location of another wireless tag (not shown inFIG. 2). For example, the network connectivity information can comprisedata indicative of one or more wireless tags that are coupled to thewireless tag 302 a, such as wireless tag 302 b. In a scenario in whichthe wireless tag 302 a embodies the wireless tag 218 a, such data can beindicative of the wireless tag 218 b. In one implementation, the dataindicative of the one or more wireless tags that are coupled to thewireless tag 302 a can be arranged in a hierarchical data structurecomprising: a top tier having data indicative of the wireless tag 302 a,which can be referred to as parent node in the hierarchy; a second tierhaving data indicative of wireless tag(s) that are directly coupled tothe wireless tag 302 a, such wireless tag(s) can be referred to aschildren node(s), one-hop wireless tag(s), or nearest-neighboringwireless tag(s); a third tier having data indicative of wireless tag(s)that are indirectly coupled to the wireless tag 302 a and directlycoupled to a wireless tag in the first tier, the wireless tag(s) in thesecond tier can be referred to as grand-children tag(s), two-hopwireless tag(s), or second-nearest-neighboring tag(s); and so forth. Itshould be appreciated that the hierarchical data structure can comprisea specific number of tiers dictated by the specific connectivity of amember associated with the wireless tag 302 a to other member(s) in anetwork. In general, the hierarchical structure can comprise M tiers,with M being an integer number greater than or equal to zero. Thescenario with M=0 represents an embodiment in which the wireless tag 302a is attached to a non-used member (e.g., 112 ₄), whereas the scenariowith M=1 represents an embodiment in which the wireless tag 302 a isattached to a first in-use member (e.g., 112 ₆) and coupled to a singlesecond in-use member (e.g., 122 ₁) in via link (e.g., link 114).

In one aspect, the topology constructor 328 can generate one or morehierarchical data structures containing the connectivity information ofa member in a network device (e.g., 110) to other members within one ormore disparate network devices (e.g., network devices 120 and 130). Inone scenario, which can be referred to as local construction scenario,generation of the one or more hierarchical structures can be completefor a plurality of network devices based on information collected byprobing a plurality of wireless units associated with the plurality ofnetwork devices. As an illustration, the local construction scenario canbe realized for a plurality of customer premises equipment (CPE) forminga closed or substantially closed confined area network (CAN) within aconfined operation area, such as a residential dwelling or a networkhub, wherein each one of the CPE can be tagged with one or more wirelesstags. In such scenario, the wireless probe 150 can collect (or otherwisereceive) location information and connectivity information for each ofthe wireless tags coupled to the plurality of CPE. In view of the closedor substantially closed nature of the CAN, the connectivity informationcan be self-contained and thus sufficient to generate a set of one ormore hierarchical data structures indicative of network topology of theCAN, such set is referred to as a complete set.

As illustrated, the wireless probe 150 can comprise a rendering unit 332that can render at least a portion of the topology information 335and/or at least a portion of data available in the data storage 336. Inone aspect, the rendering unit 332 can render such information inresponse to a change in connectivity configuration of a networkcomprising the network device, and member therein, that is tagged by thewireless tag 302 a. For instance, in one scenario, the topology server344 can push connectivity updates that can update the topologyinformation 335. The updated topology information can be rendered by therendering unit 332 in nearly real-time or after the wireless tag 302 ais probed.

In one aspect, the wireless probe 150 can transmit, via the topologyconstructor 328, for example, the set of one or more hierarchical datastructures to the topology server 344. Such set can transmitted viawireless links 337, as part of topology information.

In another scenario, which can be referred to as pseudo-localconstruction scenario, generation of the one or more hierarchicalstructures for a plurality of network devices can be accomplished basedat least on information collected by probing a plurality of wirelessunits associated with the plurality of network devices and by collectinglocation information from a repository 350, which can be remote to thelocation of the wireless probe 150. In one implementation, therepository 350 can deployed in a cloud configuration in which therepository 350 is spatially distributed, having a plurality of datastorage units (referred to as data storage sites; not shown) that form adata layer that is accessible from network elements that are local orremote to at least one (e.g., one, two, more than two, each) of theplurality of the data storage units.

As an illustration, the pseudo-local construction scenario can berealized for a plurality of equipment (e.g., QAM units) forming asemi-open CAN within a confined operation area, such as a network hub,wherein each one of the CPE can be tagged with one or more wirelesstags. The semi-open character of the CAN can arise from substantialconnectivity of at least one of the plurality of equipment with membersexternal (e.g., remote) to the CAN. In such scenario, the wireless probe150 can collect (or otherwise receive) location information and/orconnectivity information for each of the wireless tags coupled to theplurality of equipment, and, in view of the semi-open characteristic ofthe CAN, the wireless probe 150 can query the repository 350.

Accordingly, as part of generation of such data structures, the networktopology constructor 328 can query (or otherwise access) a repository350 containing topology information 354. In response, the repository350, via a data management component (not shown), can supply topologyinformation in accordance with a query received from the wireless probe150. Such information can be supplied, in one implementation, via atopology server 344, which can transmit the information to the wirelessprobe 150. As described herein, the topology server 344 can supplylocation information associated with members that are remotely locatedoutside the probe range of the wireless probe 150. The rendering unit332 can receive a connectivity update from the topology server. Inresponse, the rendering unit 332 can render data indicative of updatedtopology information.

As described herein, the topology server 344 can receive, from thewireless probe 150, location information and/or connectivity informationfor a member in a network device at a specific location. Based on thelocation information and/or connectivity information that is received,the topology server 344 can process (e.g., aggregate, encode, decode,compress, decompress, encrypt, decrypt, certain combinations thereof, orthe like) at least a portion of such information and generate networktopology information. As part of the processing, in one aspect, thetopology server 344 can manage several naming conventions of networkdevices, permitting utilization of different conventions in a mannerthat is seamless to the wireless probe 150 or other device that consumeslocation information and/or connectivity information in accordance withaspects described herein. In one aspect, the topology server 344 can mapa current wireless naming convention to an extant, legacy namingconvention that can be specific to a network layer of the networklayer(s) 246.

In one embodiment, e.g., exemplary embodiment 400, the topology server344 can comprise an aggregator unit 404 that can operate on at least theportion of the location information and/or the connectivity information.To at least such end, in one aspect, the aggregator unit 404 can operateon hierarchical data structures representative of the portion of thelocation information and/or the connectivity information. In onescenario, the aggregator unit 404 can augment a hierarchical datastructure with other data structures (hierarchical or otherwise) togenerate a larger data structure indicative of location informationand/or connectivity information of larger portions of the network 340,or network devices therein. In another scenario, the aggregator unit 404can extract a portion of a hierarchical data structure and, as a result,generate a smaller hierarchical data structure. The network topologyinformation can comprise data and/or metadata associated with locationand connectivity of a wide-area network comprising the network devicecoupled to the wireless probe 302. In one aspect, the network topologyinformation can be retained in the repository 350 in one or moreelements 354, represented with a block labeled “topology info.” Thememory element(s) 354 can be referred to as topology info 335 and can beembodied in or can comprise a register, a memory page, a file, adatabase, any combination thereof, or the like. It should be appreciatedthat the repository 350 can be included in a data storage layer includedor can be functionally coupled to a core platform (not shown) of thenetwork 340. For instance the repository 350 can be part of a contentdistribution network (CDN; not shown).

In one scenario, the topology server 344 can monitor network integrityby comparing connectivity information (e.g., data and/or metadata) withidealized (e.g., planned) network connectivity. In addition or in thealternative, the topology server 344 can diagnose operational issues bysignaling (e.g., delivering an instruction to) a first network device totransmit an information packet to a second network device designed to becommunicatively coupled to the first network device. The informationpacket can be embodied in or can comprise a data packet and/or a controlpacket, and can be delivered via a first member contained in the firstnetwork device to a second member contained in the second networkdevice. In one implementation, the information packet can be referred toas a pilot packet, and a member that receives the pilot packet canrespond (e.g., generate and transmit a response pilot packet) in aspecific manner based at least on the type of the pilot packet. In oneaspect, failure of the first network device to deliver a pilot packet tothe second network device, or failure of the second network device totransmit a response pilot packet to the first network device canindicate a root cause of an operational issue. For example, the rootcause can comprise one or more of a non-operational link, amalfunctioning network device or member thereof, combinations of theforegoing, or the like. The topology server 344 can generate a record ofthe operational failure and can retain such record in the repository350. In addition or in the alternative, in one embodiment (e.g., 400 inFIG. 4), the record of the operational failure can be retained in amemory 416 included in the topology server 344. In addition, or in thealternative, the topology server can supply the record to a wirelessprobe, such as wireless probe 150. The record, in one aspect, can beembodied or can comprise a data structure having data indicative of thefirst network device type and location, and second network device typeand location. In one embodiment, e.g., embodiment 400 in FIG. 4, thetopology server 344 can comprise a diagnostic unit 408 that can performsuch monitoring and diagnostic as described herein.

The topology server 344 can distribute (e.g., transmit) the networktopology information downstream, e.g., to the wireless probe 150 orother wireless probes, and/or upstream, e.g., to a network node in anetwork layer or another topology server. As illustrated, the networklayer can be part of one or more network layers 346 (business layer,network planning layer, customer care layer, etc.). Such distributioncan be performed, at least in part, via communication link(s)represented with open-head arrows, such link(s) can comprise one or morenetwork components (router(s), server(s), network switches(s),connector(s), hubs, etc.) that can permit communication among thetopology server 344 and a network layer of the one or more networklayers 346. In certain embodiments, the communication link(s) caninclude one or more of: a reference link (Cx, Cr, Dh, Dx, Gm, Ma, Mg, orthe like) and related components; conventional bus architectures such asaddress buses, system buses; wired links, such as high definitionmultimedia interface (HDMI) cables, fiber optic lines, coaxial lines,hybrid fiber-coaxial links, Ethernet lines, T-carrier lines,twisted-pair line, or the like, and various connectors (e.g., anEthernet connector, an F connector, a USB connector, an RS-232connector, or the like); wireless links, including one or more ofterrestrial wireless links, satellite-based wireless links, or acombination thereof; and so forth.

In one embodiment, the topology server 344 can comprise a middlewareunit 412 that can transmit network topology information to networknode(s) in the one or more network layers 346, and/or network node(s) inan external network (e.g., external network 195). Upstream distributionof the network topology information can permit integration of suchinformation into administration functions of the network 340. In certainembodiments, the topology server 344 can be located in a core platform(not shown) of the network 340. In other embodiments, the topologyserver 344 can be deployed in the field, remote to the core platform, ata specific location within the network 340. For example, the specificlocation can be the location of a hub in a content distribution network.For another example, the specific location can be the location of alast-mile aggregator in the content distribution network. In the latterexamples, the topology server 344 can be embodied in a blade computerconfigured (e.g., programmed) to implement the functionality describedherein. For yet another example, the specific location can be thelocation of a base station for macrocellular wireless communication.

As illustrated, the exemplary system 300 can comprise a device 360 thatcan manage network topology information retained in the data repository350. In one embodiment, the device 360 can be a computing device in anetwork operation center (NOC). In another embodiment, the device 360can be a computing device in an external network (e.g., a vendor'snetwork) that can provide maintenance to a deployment of the network340, or can perform network planning simulations. In yet anotherembodiment, the device 360 can be part of a customer care facility and,in one aspect, can query location information and connectivityinformation specific to a network customer (residential or commercial)in response to an operational issue experienced by the customer.

FIG. 5 is a high-level block diagram of an exemplary embodiment 500 of acomputing device 502 in accordance with one or more aspects of thedisclosure. In certain implementations, the computing device 502 canembody the topology server 544. As illustrated, the computing device 502comprises a group of one or more I/O interfaces 504, a group of one ormore processors 508, a memory 516, and a bus 512 that functionallycouples (e.g., communicatively couples) two or more of the functionalelements of the topology server 544 including the group of one or moreprocessors 508 to the memory 516. In certain scenarios, the group of oneor more processors 508 can comprise a plurality of processors that canexploit concurrent computing.

Functionality of the computing device 502 can be configured by a groupof computer-executable instructions (e.g., programming code instructionsor programming modules) that can be executed by at least one processorof the one or more processors 508. Generally, programming modules cancomprise computer code, routines, objects, components, data structures(e.g., metadata objects, data object, control objects), and so forth,that can be configured (e.g., coded or programmed) to perform aparticular action or implement particular abstract data types inresponse to execution by the at least one processor. For example, agroup of computer-executable instructions can configure logic that, inresponse to execution by the at least one processor, can enable thecomputing device 502 to operate as the topology server 128 in accordancewith aspects described herein.

Data and computer-accessible instructions, e.g., computer-readableinstructions and computer-executable instructions, associated withspecific functionality of the topology server 544 can be retained inmemory 516. As illustrated, one or more memory elements, referred to astopology record(s) 519, can be retained in memory 516 in the datastorage 520, and at least a portion of information contained in topologyinfo. 354 and/or topology info 335 in example system 300 can be retainedin the topology record(s) 519. It should be appreciated that, accordingto one or more aspects described herein, the data storage 520 cancomprise a variety of data, metadata, or both, associated with networktopology information associated with a network of functional elements.Such data and instructions can permit implementation, at least in part,of generation and/or management of network topology information inaccordance with one or more aspects of the disclosure. In one aspect,the computer-accessible instructions can embody any number ofprogramming code instructions or program modules that permit specificfunctionality. In the subject specification and annexed drawings, memoryelements are illustrated as discrete blocks, however, such memoryelements and related computer-accessible instructions (e.g.,computer-readable and computer-executable instructions), and data canreside at various times in different storage elements (registers, memorypages, files, databases, memory addresses, etc.; not shown) in memory516.

Memory 516 also can comprise one or more computer-executableinstruction(s) for implementation of specific functionality of thetopology server 344 in connection with the generation and/or managementof network topology information described herein. Suchcomputer-executable instructions can comprise topology constructioninstruction(s) 518 a and/or topology management instruction(s) 518 b. Inone aspect, as described herein, the topology constructioninstruction(s) 518 a and/or topology management instruction(s) 518 b canbe stored as an implementation (e.g., a compiled instance) of one ormore computer-executable instructions that implement and thus provide atleast the functionality of the methods described herein. The topologyconstruction instruction(s) 518 a and/or topology managementinstruction(s) 518 b also can be transmitted across some form ofcomputer readable media. It should be appreciated that differenttopology construction instruction(s) 518 a and/or topology managementinstruction(s) 518 b can render structurally alike computing devicesinto functionally different components, with functional differencesdictated by logic (e.g., computer-executable instructions and datastructures) specific to each one of such computing devices and definedby the topology construction instruction(s) 518 a and/or topologymanagement instruction(s) 518 b.

Memory 516 can be embodied in a variety of computer-readable media.Exemplary computer-readable media can be any available media that isaccessible by a processor in a computing device, such as one processorof the group of one or more processors 508, and comprises, for example,both volatile and non-volatile media, removable and non-removable media.As an example, computer-readable media can comprise “computer storagemedia,” or “computer-readable storage media,” and “communicationsmedia.” Such storage media can be non-transitory storage media.“Computer storage media” comprise volatile and non-volatile, removableand non-removable media implemented in any methods or technology forstorage of information such as computer readable instructions, datastructures, program modules, or other data. Exemplary computer storagemedia comprises, but is not limited to, RAM, ROM, EEPROM, flash memoryor other memory technology, CD-ROM, digital versatile disks (DVD) orother optical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other medium which canbe utilized to store the desired information and which can be accessedby a computer or a processor therein or functionally coupled thereto.

Memory 516 can comprise computer-readable non-transitory storage mediain the form of volatile memory, such as random access memory (RAM),electrically erasable programmable read-only memory (EEPROM), and thelike, or non-volatile memory such as read only memory (ROM). In oneaspect, memory 516 can be partitioned into a system memory (not shown)that can contain data and/or programming modules that enable essentialoperation and control of the topology server 344. Such program modulescan be implemented (e.g., compiled and stored) in memory element 522,referred to as operating system (OS) instruction(s) 522, whereas suchdata can be system data that is retained in memory element 524, referredto as system data storage 524. The OS instruction(s) 522 and system datastorage 524 can be immediately accessible to and/or are presentlyoperated on by at least one processor of the group of one or moreprocessors 508. The OS instruction(s) 522 can embody an operating systemfor the computing device. Specific implementation of such OS can dependin part on structural complexity of the computing device 502 (e.g., incertain embodiments, complexity of the topology server 344). Higherstructural complexity can afford higher-level OSs. Example operatingsystems can include Unix, Linux, iOS, Microsoft Windows® operatingsystem, and substantially any operating system for a computing device.In certain scenarios in which the computing device 502 embodies thetopology server 344, the operating system embodied in OS instruction(s)522 can have different levels of complexity based on particularconfiguration of the topology server 344.

Memory 516 can comprise other removable/non-removable,volatile/non-volatile computer-readable non-transitory storage media. Asan example, memory 516 can include a mass storage unit (not shown) whichcan provide non-volatile storage of computer code, computer readableinstructions, data structures, program modules, and other data for thecomputing device 502. A specific implementation of such mass storageunit (not shown) can depend on desired form factor of the computingdevice 502 and space available for deployment thereof. For suitable formfactors and sizes of the computing device 502, the mass storage unit(not shown) can be a hard disk, a removable magnetic disk, a removableoptical disk, magnetic cassettes or other magnetic storage devices,flash memory cards, CD-ROM, digital versatile disks (DVD) or otheroptical storage, random access memories (RAM), read only memories (ROM),electrically erasable programmable read-only memory (EEPROM), or thelike.

Features of generation and/or management of network topology informationdescribed herein can be performed, at least in part, in response toexecution of software components by a processor. The software componentscan include one or more implementations of the topology constructioninstruction(s) 518 a and/or topology management instruction(s) 518b—e.g., topology construction instruction(s) 518 a and/or topologymanagement instruction(s) 518 b compiled with different compilers. Inparticular, yet not exclusively, to provide the specific functionalityof the computing device 502, a processor of the one or more processors508 can execute at least a portion of the computer-accessibleinstructions in topology construction instruction(s) 318 a and/ortopology management instruction(s) 518 b. In certain embodiments, thememory 516 can have computer-executable instructions encoded thereon,such instructions embodying or comprising an implementation of thetopology construction instruction(s) 518 a and/or topology managementinstruction(s) 518 b.

In general, a processor of the group of one or more processors 508 canrefer to any computing processing unit or processing device comprising asingle-core processor, a single-core processor with software multithreadexecution capability, multi-core processors, multi-core processors withsoftware multithread execution capability, multi-core processors withhardware multithread technology, parallel platforms, and parallelplatforms with distributed shared memory (e.g., a cache). In addition orin the alternative, a processor of the group of one or more processors508 can refer to an integrated circuit with dedicated functionality,such as an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), acomplex programmable logic device (CPLD), a discrete gate or transistorlogic, discrete hardware components, or any combination thereof designedto perform the functions described herein. In one aspect, processorsreferred to herein can exploit nano-scale architectures such as,molecular and quantum-dot based transistors, switches and gates, inorder to optimize space usage (e.g., improve form factor) or enhanceperformance of the computing devices that can implement the variousaspects of the disclosure. In another aspect, the one or more processors508 can be implemented as a combination of computing processing units.

The one or more input/output (I/O) interfaces 504 can functionallycouple (e.g., communicatively couple) the topology server 344 to anotherfunctional element (component, unit, server, gateway node, repository,etc.), for example. Functionality of the topology server 344 that isassociated with data I/O or signaling I/O can be accomplished inresponse to execution, by a processor of the group of one or moreprocessors 508, of at least one L/O interface retained in memory element528. Such memory element is represented by the block I/O interface(s)528. In some embodiments, the at least one I/O interface embodies an APIthat permits exchange of data or signaling, or both, via an I/Ointerface of I/O interface(s) 504. In certain embodiments, the one ormore I/O interfaces 504 can include at least one port that can permitconnection of the topology server 344 to other functional elements ofthe example system 300. In one or more scenarios, the at least one portcan comprise network adaptor(s) such as those present in referencelinks, and other network nodes. In other scenarios, the at least oneport can include one or more of a parallel port (e.g., GPIB, IEEE-1284),a serial port (e.g., RS-232, universal serial bus (USB), FireWire orIEEE-1394), an Ethernet port, a V.35 port, or the like. The at least oneI/O interface of the one or more I/O interfaces 504 can enable deliveryof output (e.g., output data, output signaling) to such functionalelements. Such output can represent an outcome or a specific action ofone or more actions described herein, such as the actions in one or moreof the methods illustrated in FIG. 9 through FIG. 12.

In certain embodiments, the topology server 344 can comprise afunctionality specific platform (not shown) which can include one ormore components that enable the functionality of the computing device502. In an embodiment in which the computing device 502 embodies thetopology server 344, a component of the one or more components can be afirmware component having dedicated resources (e.g., a processor,software, etc.) to implement certain functions that supportimplementation of or implement at least part of the functionality of thetopology server 344. In another embodiment, the functionality specificplatform can include at least a portion of the one or more processors508 which can be dedicated to execution of a part or all of the topologyconstruction instruction(s) 318 a and/or topology managementinstruction(s) 518 b, thus relieving at least some of the computationalload from the one or more processors 508 for other operation of thecomputing device 502.

Bus 512, and the various configurations thereof, represents one or moreof several types of bus structures, including a memory bus or memorycontroller, a peripheral bus, an accelerated graphics port, and aprocessor or local bus using any of a variety of bus architectures. Asan example, such architectures can comprise an Industry StandardArchitecture (ISA) bus, a Micro Channel Architecture (MCA) bus, anEnhanced ISA (EISA) bus, a Video Electronics Standards Association(VESA) local bus, an Accelerated Graphics Port (AGP) bus, and aPeripheral Component Interconnects (PCI), a PCI-Express bus, a PersonalComputer Memory Card Industry Association (PCMCIA), Universal Serial Bus(USB), and the like.

FIG. 6A illustrates an example embodiment 600 of a wireless device 602that can operate in accordance with at least certain aspects describedherein. In one aspect, the wireless device 602 can embody a wirelessprobe, such as wireless probe 302. In another aspect, the wirelessdevice 602 can embody a wireless probe, such as wireless probe 150. Topermit wireless communication, the wireless device 602 includes a radiounit 608 having one or more antennas 612 and a communication unit 616.As illustrated in exemplary embodiment 650 shown in FIG. 6A, thecommunication unit 616 can comprise a set of one or moretransmitters/receivers 656, and components therein (amplifiers, filters,etc.), functionally coupled to a communication (comm.) processing unit660. In certain implementations, such processing unit can comprise amodulator/demodulator (mod/demod) unit (also referred to as modem), amultiplexer/demultiplexer (mux/demux) unit, and a coder/decoder unit(also referred to as codec). Each of the transmitter(s)/receiver(s) 756can transmit and receive wireless signal via the one or more antennas612. It should be appreciated that the architecture of the communicationprocessing unit 660 can be specific to the functional complexity of thewireless device 602. For example, in a scenario in which the wirelessdevice 602 embodies a wireless tag, such as example embodiment 700illustrated in FIG. 7A, the complexity of the communication unit 616 canbe lower than the complexity of such unit in a scenario in which thewireless device 602 embodies a wireless probe, such as wireless probe150 as illustrated in example embodiment 800 in FIG. 8A. It should alsobe appreciated that complexity of the transmitter(s)/receiver(s) 656 canbe specific to complexity of the wireless device 602. For instance, thetransmitter(s)/receiver(s) 756 in embodiment 750, illustrated in FIG.7B, can be less complex that the transmitter(s)/receiver(s) 856 inembodiment 850, illustrated in FIG. 8B.

Electronic components and associated circuitry of the communicationprocessing unit 660 can permit processing and manipulation, e.g.,coding/decoding, deciphering, modulation/demodulation, of signal(s)received by the wireless device 602 and signal(s) to be transmitted bythe wireless device 602. In one aspect, received or transmitted wirelesssignal(s) can be modulated and coded, or otherwise processed, inaccordance with one or more radio technology protocols (e.g., 3rdGeneration Partnership Project (3GPP) Universal Mobile TelecommunicationSystem (UMTS), 3GPP Long Term Evolution (LTE), or the like). Theelectronic components in the communication unit 616, including the oneor more transmitters/receivers 656, can exchange information (e.g.,data, code instructions, signaling and related payload data, or thelike) through a bus (represented with a double-headed arrow), which canembody or comprise at least one of a system bus, an address bus, a databus, a message-passing bus, a power bus, a reference link or interface,a combination thereof, and the like. Each of the one or moretransmitters/receivers 656 can convert signal from analog to digital andvice versa. In addition or in the alternative, thetransmitter(s)/receiver(s) 656 can divide a single data stream intomultiple parallel data streams, or perform the reciprocal operation.Such operations may be conducted as part of various multiplexingschemes.

In certain embodiments, as illustrated in FIG. 7B and FIG. 8B, thecommunication processing unit 660 can comprise a mux/demux unit (e.g.,mux/demux unit 764 or mux/demux unit 864) that is functionally coupledto the one or more receivers/transmitters 656 and can permit processingof signal(s) in time and frequency domain. In one aspect, the mux/demuxunit can multiplex and demultiplex information (e.g., data, signaling,or both) according to various multiplexing schemes such as time divisionmultiplexing (TDM), frequency division multiplexing (FDM), orthogonalfrequency division multiplexing (OFDM), code division multiplexing(CDM), space division multiplexing (SDM). In addition or in thealternative, in another aspect, the mux/demux component 308 can scrambleand spread information (e.g., codes) according to substantially anycode; e.g., Hadamard-Walsh codes, Baker codes, Kasami codes, polyphasecodes, and so on. As described herein, the communication processing unit660 can comprise a modem (e.g., modem 760 or modem 860) that canmodulate and demodulate information (e.g., data, signaling, or both)according to various modulation techniques, such as frequency modulation(e.g., frequency-shift keying), amplitude modulation (e.g., M-aryquadrature amplitude modulation (QAM), with M a positive integer;amplitude-shift keying (ASK)), phase-shift keying (PSK), and the like).In addition, processor(s) 622 can enable, at least in part, the wirelessdevice 602 to process data (e.g., symbols, bits, or chips) formultiplexing/demultiplexing, modulation/demodulation, such asimplementing direct and inverse fast Fourier transforms, selection ofmodulation rates, selection of data packet formats, inter-packet times,etc.

The communication processing unit 660 can comprise a codec (e.g., codec768 or codec 868) that can operate on information (e.g., data,signaling, or both) in accordance with one or more coding/decodingschemes suitable for communication, at least in part, through the one ormore transmitters/receivers 656. In one aspect, the coding/decodingschemes, or related procedures, can be retained as a group of one ormore computer-executable instructions in memory 630. In a scenario inwhich wireless communication among the wireless device 602 and a device(e.g., a wireless tag or a wireless probe) utilizes multiple-inputmultiple-output (MIMO), multiple-input single-output (MISO),single-input multiple-output (SIMO) or single-input single-output (SISO)operation, the codec can implement at least one of space-time blockcoding (STBC) and associated decoding; or space-frequency block (SFBC)coding and associated decoding. It should be appreciated that one ormore such functionalities of the codec can be available in embodimentsof certain complexity. For instance, in an example scenario in which thewireless device 602 embodies a wireless tag (e.g., wireless tag 218 a)with low complexity, wireless communication according to MIMO, MISO, orSIMO, may not available.

In addition or in the alternative, the codec can extract informationfrom data streams coded in accordance with spatial multiplexing scheme.In one aspect, to decode received information (data, signaling, orboth), the codec 312 can implement at least one of computation oflog-likelihood ratios (LLR) associated with constellation realizationfor a specific demodulation; maximal ratio combining (MRC) filtering,maximum-likelihood (ML) detection, successive interference cancellation(SIC) detection, zero forcing (ZF) and minimum mean square errorestimation (MMSE) detection, or the like. The codec can employ, at leastin part, a mux/demux unit and a mod/demod unit contained in thecommunication processing unit 660 in order to operate in accordance withaspects described herein.

The wireless device 602 can operate in a variety of wirelessenvironments having wireless signals conveyed in differentelectromagnetic radiation (EM) frequency bands. To at least such end,the communication unit 616 can process (code, decode, format, etc.)wireless signal(s) within a set of one or more EM frequency bands (alsoreferred to as frequency bands) comprising one or more of radiofrequency (RF) portions of the EM spectrum, microwave portion(s) of theEM spectrum, or infrared (IR) portion of the EM spectrum. In one aspect,the set of one or more frequency bands can include at least one of (i)all or most licensed EM frequency bands, or (ii) all or most unlicensedfrequency bands currently available for telecommunication.

In the illustrated embodiment, the wireless device 602 comprises amemory 630 and one or more processors 622 functionally coupled to thememory 630. In one aspect, the functional coupling is provided via a bus637. The memory 630 can comprise one or more memory elements 632comprising computer-executable instructions encoded thereon. Such memoryelements are labeled “functionality specific elements” and, in responseto execution by one of the one or more processors 622, can enable atleast specific functionality of the wireless device 602. In addition orin the alternative, the memory 630 can comprise a data storage 636 thatcan contain information (e.g., data and/or metadata) associated withgeneration and/or management of network topology information accordingto aspects described herein. It should be appreciated that the datastorage 636 can be specific to an implementation of the wireless device602. In an implementation in which the wireless device 602 embodies awireless tag, such as example embodiment 700 in FIG. 7A, the datastorage 636 can comprise one or more IDs 311, location 312, type 313,and one or more address(es) 314, and connectivity 315. In certainimplementations, at least a portion of the data storage 636 can beretained in a removable element, such as a subscriber identificationmodule (SIM) card storage, a universal integrated circuit card (UICC)storage, or a removable user identity module (RUIM). In animplementation in which the wireless device 602 embodies the wirelessprobe 150, such as example embodiment 800 in FIG. 8A, the data storage636 can comprise topology info. 335 and data storage 336.

In certain implementations, a processor of the one or more processors622 can be configured, by the computer-executable instructions, toreceive data wirelessly from a plurality of wireless tags. As describedherein, the plurality of wireless tags can be embodied in a plurality ofRFID devices, wherein at least one of the RFID devices of the pluralityof RFID devices being coupled to a selected location in a network deviceof a communication network. The computer-executable instructions alsocan configure the processor to generate a network topology of theplurality of RFID devices based at least on a portion of the data, thedata comprising location information associated with at least one ofplurality of RFID devices. The network topology can comprise dataindicative of each location of each one of the plurality of RFIDdevices. The network topology comprises a connectivity map having dataindicative of one of presence or absence of a connection among at leasttwo RFID devices of the plurality of RFID devices, wherein theconnection is one of a physical connection or a logical connection.

In one aspect, the processor can be further configured to supply atleast a portion of the network topology to a network element in thecommunication network. In addition or in the alternative, the processorcan be configured to cause an electronic device to render the networktopology. In another aspect, the processor can be configured toimplement a naming convention for identifying each one of the pluralityof RFID devices. In yet another aspect, the processor can be configuredto update the network topology in response to addition or removal of anRFID device from the plurality of RFID devices. In still another aspect,the processor can be configured to cause a device (e.g., wireless device602) to refresh a rendering of an extant network topology in response toan update to the extant network topology.

As illustrated, the wireless device 602 comprises one or more processors622 which can permit, at least in part, functionality of one or morefunctional elements of the wireless device 602 in accordance with atleast certain aspects described herein. The one or more processors 622can be functionally coupled to each functional element within thewireless device 602 and to the memory 630 via the bus 637. In certainimplementations, the bus 637 can be embodied in one or more of: a memorybus, a system bus, an address bus, a message-passing bus, a power bus,or one or more reference links or interface(s). While in embodiment 600,the one or more processors 622 are illustrated as external to thefunctionality specific platform 618, in an additional or an alternativeembodiment, at least one of the one or more processors 622 can beintegrated into such platform. In one implementation in which thewireless device 602 embodies a wireless tag, e.g., such as exampleembodiment 700 in FIG. 7A, the functionality specific platform cancomprise or can be embodied in a tagging unit 708 and a proximitydetection unit 712, which can have the functionality of tagging unit 304and proximity detection unit 309, respectively. It should be appreciatedthat, in some embodiment(s), one or more of the tagging unit 708 or theproximity detection unit 712 can reside within the memory 630 as one ormore sets of computer-accessible instructions, e.g., computer-readablecomputer-executable instructions. Such instructions, in response toexecution by a processor of the one or more processors 714, canimplement the functionality of the tagging unit 708 and/or the proximitydetection unit 712 in accordance with aspects of the disclosure. Inanother implementation in which the wireless device 602 embodies awireless probe, e.g., such as example embodiment 700 in FIG. 8A, thefunctionality specific platform can comprise or can be embodied in atopology constructor 808 and a rendering unit 810, which can have thefunctionality of topology constructor 328 and rendering unit 332,respectively. The rendering unit 332 can be contained in the one or moreI/O interface(s) 802. It should be appreciated that, in someembodiment(s), one or more of the topology constructor 808 or therendering unit 810 can reside within the memory 630 as one or more setsof computer-accessible instructions, e.g., computer-readablecomputer-executable instructions. Such instructions, in response toexecution by a processor of the one or more processors 714, canimplement the functionality of the tagging unit 708 and/or the proximitydetection unit 712 in accordance with aspects of the disclosure.

In view of the various aspects of generation of network topologyinformation for a network of assets, and management of such informationdescribed herein, example methods that can be implemented in accordancewith the disclosure can be better appreciated with reference to theflowcharts in FIG. 9 through FIG. 12. For simplicity of explanation, theexample methods disclosed herein are presented and described as a seriesof actions (also referred to as steps), pictorially represented with ablock. However, it is to be understood and appreciated thatimplementation, and related advantages, of such methods is not limitedby the order of actions, as some actions may occur in different ordersand/or concurrently with other actions from that shown and describedherein. For example, the various methods (also referred to as processes)of the disclosure can be alternatively represented as a series ofinterrelated states or events, such as in a state diagram. Moreover,when disparate functional elements (network nodes, units, etc.)implement different portions of the methods of the disclosure, aninteraction diagram or a call flow can represent such methods orprocesses. Furthermore, not all illustrated actions may be required toimplement a method in accordance with the subject disclosure.

The method(s) disclosed throughout the subject specification and annexeddrawings can be retained, or stored, on an article of manufacture, orcomputer-readable non-transitory storage medium, to facilitatetransporting and transferring such methods to computing devices (e.g.,desktop computers, mobile computers, wearable computers, mobiletelephones, and the like) for execution, and thus implementation, by aprocessor or for storage in a memory.

FIG. 9 is a flowchart of an exemplary method 900 for providing networktopology information in accordance with one or more aspects of thedisclosure. One or more blocks of the exemplary method 900 can beimplemented (e.g., performed or executed) by a computing device, such asthe wireless probe 150, or a processor integrated therein orfunctionally coupled thereto. At block 910, deployment information isreceived from a plurality of devices, wherein at least one of theplurality of devices is connected to a selected network location. Forexample, the plurality of devices can be wireless devices thatcommunicate through a wireless network. In one aspect, the deploymentinformation can comprise data and/or metadata indicative of one or moreof location information of the plurality of devices or connectivityinformation between at least two devices of the plurality of devices. Atblock 920, topology information indicative of the plurality of devicesis generated based the deployment information. For example, the topologyinformation can be generated based on some or all of the deploymentinformation. At block 930, at least a portion of the topologyinformation is supplied to a network node in the network. In oneembodiment, such information can be supplied to a server deployed (e.g.,installed and provisioned) in the network. For example, the server canbe or can comprise the topology server 344.

FIG. 10 is a flowchart of an exemplary method 1000 for updating networktopology information in accordance with one or more aspects of thedisclosure. In one aspect, the subject example method can be implemented(e.g., executed) in response to changes in deployment of a wireless tagfunctionally coupled to an asset in a network. For example, a wirelessprobe in accordance with one or more aspects described herein, such asthe wireless probe 150, or a processor integrated therein orfunctionally coupled thereto can implement the subject example method1000. At block 1010, data is received (e.g., wirelessly) from a currentplurality of devices (e.g., wireless devices), wherein at least one ofthe plurality of devices is coupled to a selected location in a network.At block 1020, it is determined if the current plurality of devices hasan additional device with respect to a previous plurality of devices. Inthe affirmative case, flow is directed to block 1070. In thealternative, in the negative case, it is determined at block 1030 if thecurrent plurality has a deficit of at least one device with respect to apreviously detected plurality of devices. In the affirmative outcome ofblock 1030, flow is directed to block 1070. In the negative outcome,flow is directed to block 1040, at which it is determined if a previousnetwork topology representing the previously detected plurality ofdevices is available. In the affirmative case, at block 1050, theprevious network topology is accessed. In the alternative, at block1060, a network topology representing the previously detected pluralityof devices is generated based at least on a portion of the data.

At block 1070, a network topology of the current plurality of devices isgenerated based at least on a portion of the data received at block1010. At 1080, topology data indicative of at least a portion of thenetwork topology is supplied to a network node (e.g., an applicationserver in an application layer) in the network.

It should be appreciated that the generating action at blocks 1060 and1070 can comprise generating connectivity information associated withone or more pathways between a first end of a link and a second end ofthe link, as described herein.

FIG. 11 is a flowchart of an exemplary method 1100 for providing networktopology information in accordance with one or more aspects of thedisclosure. One or more blocks of the exemplary method 900 can beimplemented (e.g., performed or executed) by a computing device, such asthe topology server 344, or a processor integrated therein orfunctionally coupled thereto. At block 1110, data indicative of one ormore of location of a first network member and/or connectivity of thefirst network member to at least one second network member (e.g., aset-top box) is received. In one aspect, the first network member can becontained in a first network device (e.g., a cable modem) and a secondnetwork member of the at least one second network member can becontained in a second network device (e.g., a set-top box). At block1120, network topology information is generated based on at least aportion of the data.

At block 1130, the network topology information is managed. Block 1130can be referred to as a managing action and, in one aspect, can comprisetransmitting at least the portion of the network topology information toa computing device functionally coupled to a network (e.g., network 190)comprising at least the first network member. In one embodiment, thecomputing device can be contained in an external network (e.g., externalnetwork 195). Thus, transmitting such information to the computingdevice can comprise transmitting at least the portion of the networktopology information to the external network. In another embodiment, thecomputing device can be contained in a higher network layer of thenetwork comprising at least the first network member, thus transmittingsuch information to the computing device can comprise transmitting atleast the portion of the network topology information to the highernetwork layer.

FIG. 12 is a flowchart of an exemplary method 1200 for providingtopology information. As part of the method 1200, several devices (e.g.,a first device, a second device, and a third device) can be incommunication. For example, each of the devices can be assigned, atleast for a time, to a logical address in a network. In one aspect, thelogical address can be an internet protocol version 4 or internetprotocol version 6 address. At block 1210, a signal can be received tothe second device from the third device. As an example, the signal canbe a wireless signal. At block 1220, the signal can be converted topower for the second device. For example, the signal can be converted topower through electromagnetic induction. In one aspect, one or more ofthe first device, second device, and third device can comprise a radiofrequency identification device (RFID).

At block 1230, a first device can be detected by a second device. In oneaspect, the first device can be located proximate to a first networkport, and the second device can be located proximate to a second networkport. The first network port and second network port can be located on awire or other device (e.g., router, network card). Additionally, thefirst network port and the second network port can be configured to forma network connection. For example, one of the first network port andsecond network port can be a male plug and the other can be a femaleconnector configured to receive the plug. In another aspect, the firstnetwork port and second network port can each be a used connector of thenetwork, a non-used connector of the network, a used port of thenetwork, or a non-used port of the network. For example, a usedconnector can be a port or connector coupled to another port orconnector such that network communication is enabled. A non-usedconnector can be a port or connector not connected to another port orconnector. The first device and the second device can be separatelycoupled (e.g., attached, glued, embedded) to one or more of userequipment, customer premises equipment, a server, a data storage, aconnection link, and the like.

At block 1240, data can be provided indicative of at least one of,location of the second device and connectivity of the second networkport through the network connection to the first network port. Forexample, data can be collected and stored on the second device. In oneaspect, data can comprise global positioning system information, ahistory of interactions (e.g., network connectivity) with other devices,and the like. In one aspect, the data can be provided as part of thetopology information described above. As an example, the data can beprovided to a device (e.g., the third device, a server) configured togenerate topology information based on the data. The topologyinformation can be about the first device, second device, and aplurality of other devices. The topology information can comprise, forexample, a connectivity map comprising data indicative of presence orabsence of a connection among at least two devices (e.g., the firstdevice and second device) of the plurality of devices. In one aspect,the connection can be one of a physical connection or a logicalconnection.

In view of the subject specification and annexed drawings, when comparedwith conventional approaches for generation of network topologyinformation and management thereof, various advantages emerge. Forexample, one embodiment of the disclosure can provide access toconnectivity information associated with all or most all taggedequipment at a consumer site (e.g., a residential customer site or acommercial customer site). As a result, the disclosure can permitaddressing operational issues expeditiously, with ensuing reduction ofcost and time associated with network service, and increased quality ofcustomer service and increased customer satisfaction. For anotherexample, another embodiment of the disclosure can permit integration ofnetwork topology information with administrative network layers, thuspermitting remote assessment of network performance, with the ensuingreduction of costs associated with visitation of a field facility (e.g.,a hub, an aggregator site, a base station site, or the like) forassessment and maintenance. For yet another example, other embodimentsof the disclosure can permit monitoring of asset connectivity (e.g.,fiber optic connectivity) in nearly real-time, according to apredetermined schedule, or in response to specific events, such asdeployment changes in a network comprising tagged assets in accordancewith aspects of the disclosure, or delivery of a status paging messageto a specific portions of the network.

In certain embodiment(s), one or more of the disclosed systems,apparatuses, or devices can implement one or more features of the of thedisclosure by applying artificial intelligence (AI) techniques, such asmachine learning and iterative learning, to generate an inference.Examples of such techniques include, but are not limited to, expertsystems, case based reasoning, Bayesian networks, behavior based AI,neural networks, fuzzy systems, evolutionary computation (e.g., geneticalgorithms), swarm intelligence (e.g., ant algorithms), and hybridintelligent systems (e.g., expert inference rules generated through aneural network or production rules from statistical learning).

While the systems, apparatuses, and methods have been described inconnection with exemplary embodiments and specific examples, it is notintended that the scope be limited to the particular embodiments setforth, as the embodiments herein are intended in all respects to beillustrative rather than restrictive.

Unless otherwise expressly stated, it is in no way intended that anyprotocol, procedure, process, or method set forth herein be construed asrequiring that its acts or steps be performed in a specific order.Accordingly, in the subject specification and annexed drawings, where adescription of a protocol, procedure, process, or method does notactually recite an order to be followed by its acts or steps or it isnot otherwise specifically stated in the claims or descriptions that thesteps are to be limited to a specific order, it is no way intended thatan order be inferred, in any respect. This holds for any possiblenon-express basis for interpretation, including: matters of logic withrespect to arrangement of steps or operational flow; plain meaningderived from grammatical organization or punctuation; the number or typeof embodiments described in the specification or annexed drawings, orthe like.

It will be apparent that various modifications and variations can bemade without departing from the scope or spirit of the subjectdisclosure. Other embodiments will be apparent from consideration of thespecification and practice disclosed herein. It is intended that thespecification and examples be considered as non-limiting illustrationsonly, with a true scope and spirit of the subject disclosure beingindicated by the following claims.

What is claimed is:
 1. A method, comprising: receiving data from acurrent plurality of wireless devices, wherein at least one of thecurrent plurality of wireless devices is coupled to a selected locationin a network; determining if the current plurality of wireless deviceshas an additional device with respect to a previously detected pluralityof wireless devices; generating a network topology of the currentplurality of wireless devices based at least on a portion of the data inresponse to determining that the current plurality of wireless devicesdoes have the additional device with respect to the previously detectedplurality of wireless devices; and transmitting topology data indicativeof at least a portion of the network topology to a network node.